IBX Connect - Duplicate check
In the following two common scenarios are described where transactions are rejected by the IBX Connect platform due duplicate check errors. The sender is notified about those events synchronously with an HTTP response (HTTP response code usually: 400) including a SOAP response with a brief error description.
Duplicate check with default HTTP responses
The messageID in the SOAP envelope
("nsprop:identity") in combination with senderID and
document type is not unique:
Response example
The document number (ordernumber, invoicenumber) in the
XML payload (business document) in combination with
senderID, document type (order or invoice only) is not
unique (the document has been processed successfully
before):
Response example
Instructions for downloading files from this site